-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed issue with lack of clear message for erroneous suite definition #432
Conversation
client/client-scripts/aet.sh
Outdated
@@ -81,8 +81,9 @@ function process_locked_suite { | |||
((UNLOCK_TIMEOUT-=5)) | |||
start_suite | |||
else | |||
errorMessage=$(echo $body | jq -r ".errorMessage") | |||
echo "Unsuccessful Request to \"$endpoint$SUITE_ENDPOINT\", status: $code |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please change the message to:
"Unsuccessful Request to "$endpoint$SUITE_ENDPOINT", status: $code, error: $errorMessage"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
tested, working well ✔️ |
Description
Fixed issue with lack of clear message for erroneous suite definition.
Motivation and Context
Before that fix, if there were errors in the response, they were returned in HTML format, containing a lot of unnecessary fluff.
This bugfix changes that, so that the response in JSON format is returned (as it has been the case for successful response). The aet.sh script has also been modified to accommodate that change.
ISSUE 414
Screenshots (if appropriate)
Upgrade notes (if appropriate)
Types of changes
Checklist:
I hereby agree to the terms of the AET Contributor License Agreement.